1.3. Third set of comments

1. One vendor requires a principal resource with the CALDAV:calendar-home-set property so that it can locate a user’s calendar collections. The developer added support to their application for WEBDAV principals (section 4 of the ACL spec).

   One application had problems renaming calendars. This operation uses WEBDAV MOVE underneath. It turns out that the application was sending a relative URI in the Destination header which RFC 2518 specifies must contain an absolute URI. The developer beefed up the code to handle both forms and I believe the folks changed to absolute, so all was well after that.

2. One vendor did some amount of testing with their application, but the developer wasn’t directly involved and they never communicated any issues to him.

3. Another vendor ran the CALDAV test suite from their calendar server and found an issue when DELETEing a null resource.

4. An unknown party exposed a bug wherein a vendor application errored when receiving any CALDAV REPORT against a regular (non-calendar) collection.

The developer fixed all of these issues yesterday and then waited to hear about anything else that came up the next day. Nothing was reported.